Hi and thanks for your efforts in testing to improve. I've tested with a single high-res dataset (slightly above 4k) but couldn't really confirm better visual results. PSNR is oscillating a lot in this dataset which is why I cannot compare those values. I think it might also depend on how images were taken/are aligned? Could you share some more details about your datasets where you experience improvements?

Interesting, If I have free time, I will try this implementation and share the result...

My Experiment:

Desolation dataset

Images size: 1899x1064
Already processed by colmap image_undistorter, then Recreating sparse_pc.ply and transforms.json.
Using splatfacto-big & antialiased rasterizer.

Blue : without coarse to fine training

ns-train splatfacto-big --logging.steps-per-log 200 --vis viewer+wandb --viewer.websocket-port 7007 \
    --pipeline.model.rasterize_mode antialiased \
    nerfstudio-data \
    --data path/to/scene --downscale-factor 1

Red : with coarse to fine training

ns-train splatfacto-big --logging.steps-per-log 200 --vis viewer+wandb --viewer.websocket-port 7007 \
    --pipeline.model.rasterize_mode antialiased \
    --pipeline.model.resolution-schedule 3000 \
    --pipeline.model.num-downscales 2 \
    nerfstudio-data \
    --data path/to/scene --downscale-factor 1

My Second Experiment:

Truck dataset

Images size: 3904x2176 ((has been enlarged 4 times with Waifu4X super resolution))
Already processed by colmap image_undistorter, then Recreating sparse_pc.ply and transforms.json.
Using splatfacto-big & classic rasterizer.

Blue : without coarse to fine training

ns-train splatfacto-big --logging.steps-per-log 200 --vis viewer+wandb --viewer.websocket-port 7007 \
    nerfstudio-data \
    --data path/to/scene --downscale-factor 1

Red : with coarse to fine training

ns-train splatfacto-big --logging.steps-per-log 200 --vis viewer+wandb --viewer.websocket-port 7007 \
    --pipeline.model.resolution-schedule 3000 \
    --pipeline.model.num-downscales 2 \
    nerfstudio-data \
    --data path/to/scene --downscale-factor 1

Like @jb-ye being said:

One counter-intuitive phenomenon is when training at higher resolution, splatfacto actually creates less gaussians.

Yes, it seems right. lower resolution (976x544) has higher gaussians than current repo & this PR too. Please see black line

good work! I also have similar findings, at high resolution, shooting high frequency signal(sofa part), when the image is downsampled, the Gaussian distribution is more (left is original, right is downsampled)

good work! I also have similar findings, at high resolution, shooting high frequency signal(sofa part), when the image is downsampled, the Gaussian distribution is more (left is original, right is downsampled)

Did this PR improve your results at the original resolution?

good work! I also have similar findings, at high resolution, shooting high frequency signal(sofa part), when the image is downsampled, the Gaussian distribution is more (left is original, right is downsampled)

Did this PR improve your results at the original resolution?

I haven't tried it yet. I'll let you know when I get the results.

My Third Experiment:

Purancak dataset (Private Dataset)

Images size: 2000x1500
Already processed by ns-process-data image --data /path/to/images --output-dir /path/to/output --skip-image-processing, then copying original images to output-dir.
Using splatfacto & classic rasterizer.

Blue : without coarse to fine training

ns-train splatfacto --logging.steps-per-log 200 --vis viewer+wandb --viewer.websocket-port 7007 \
    nerfstudio-data \
    --data path/to/scene --downscale-factor 1

Red : with coarse to fine training

ns-train splatfacto --logging.steps-per-log 200 --vis viewer+wandb --viewer.websocket-port 7007 \
    --pipeline.model.resolution-schedule 3000 \
    --pipeline.model.num-downscales 2 \
    nerfstudio-data \
    --data path/to/scene --downscale-factor 1

It gives a little bit improvement so far in my third experiment. @jb-ye